Great job, thank you very much, I'm interested in INA228 support myself. Will there be binaries available for download for the ESP32?

Will there be binaries available for download for the ESP32?

Assuming you mean ESP32-Classic, here are the builds that this plugin is included in:

ESP_Easy_mega_20251228_energy_ESP32_4M316k-2.zip for ESP32 with 4MB Flash
ESP_Easy_mega_20251228_max_ESP32_16M8M-2.zip for ESP32 with 16MB Flash

Both include the OTA .bin and the Serial-flashable .factory.bin (address 0x0).

Edit: Re-uploaded the zip files (appended -2) with the adjusted Conversion rate settings I pushed a few minutes ago.

NB: Possibly the INA228 Power setting might not return the expected result, as the code shows a TODO there... 🤔

Thanks for the binaries. I loaded the 4M316k.factory module, and it boots up, but I doubt it will work correctly. There's no option to select the shunt value. Without checking the documentation, I'm not entirely sure if all the INA3221/INA226/INA228/INA231/INA260 models have the same registers. At first glance, the INA3221 is a 3-channel model, while the others aren't. So how would this work without selecting the INA model in the plugin?

So how would this work without selecting the INA model in the plugin?

Not sure what/how you installed the binary, but the P132 plugin ("Energy (DC) - INA3221/INA226/INA228/INA231/INA260") should show an INA type selector, where you can choose what INA chip is used on the board, and ditto for the Shunt resistor value (that selector was already available in the original version of the plugin, and now has 2 extra values added).
Can you show a screenshot of the device configuration for the plugin? Does it show the name of the build near the bottom-right end of the web page? It should be of today, 20251228, as I made a fresh build (also reflected in the name of the .zip files).

Ah, this is a phenomenon we sometimes see when some other firmware (ESPHome, Espruna, Tasmota?) has been used on the esp, and the flash hasn't been wiped before installing ESPEasy. It tries to re-use an existing file system, but if that's too small it fails in writing the configuration file(s), causing weird behavior and/or crashed like you have shown.
Solution: First wipe the entire flash, you can do that using the web-flasher at https://td-er.nl/ESPEasy/latest, flash the last Energy build on it, connect to WiFi as usual and then install the above build via OTA (Tools/Firmware update) using the .bin file (not the .factory.bin file). Your current configuration is crooked anyway, so starting from scratch is the best way to solve that.

Thank you again for your involvement and willingness to help. It's possible this is a hardware issue with my ESP32; none of the methods I know of for clearing the memory have yielded positive results. Since I only have one ESP32 board (I have many, but they're ESP8266s), I've ordered another ESP32, but it will probably take some time for them to arrive.

I have many, but they're ESP8266s

I've built you a Custom Energy build with this feature enabled for ESP8266 with 4MB Flash:
ESP_Easy_mega_20251229_energy_ESP8266_4M1M.zip
(The .bin.gz is a gzipped version of the .bin file, for faster upload via OTA, allow about 20 seconds after the OTA upload has finished so the data is unpacked in the correct flash location)

Another huge thank you. The ESP8266 binary is better. Almost everything seems to work, but there's a problem with reading data. Admittedly, I've been experimenting with the INA226 for a while now. I have a question: instead of selecting the internal resistor value, there should be an option to select a shunt, e.g., 30A (75mV), etc., because these built-in resistors are intended for small pads.

Selecting a different shunt resistor is mostly a wiring issue, finding the right shunt value (for 30A the 2 mOhm setting should be just right for an INA226), find a 0.002 Ohm resistor that can handle the power dissipation, remove the existing shunt from the board and wire the new shunt to the board.
Currently 0.002 Ohm is the smallest shunt supported, (and previously 0.005 Ohm was the smallest, allowing ca. 16A), but nobody ever asked for smaller or more flexible configuration (the plugin was available in the ESPEasy PluginPlayground before we added it to ESPEasy), so until now there was no reason to change that 🤔

I don't care about such currents, but this connector allows you to select a current in the range [1-1022 A], but there's still no option to change the shunt, and that's where I see a lack of consistency. A while ago, a similar build for the ESP8266 and INA226 was posted on the forum, with the option to change the shunt to an external one. Again, I don't care about that.

I was referring to shunts like these, of course, for larger currents. Because looking for a resistor for, say, 50A is a bad idea.

https://www.aliexpress.us/item/3256804424770086.html?spm=a2g0o.productlist.main.1.632873732aYBoc&aem_p4p_detail=202512291139502324835655535800004893540&algo_pvid=0783ecf9-0244-4408-ac5c-10685ca9d8b6&algo_exp_id=0783ecf9-0244-4408-ac5c-10685ca9d8b6-0&pdp_ext_f=%7B%22order%22%3A%22198%22%2C%22eval%22%3A%221%22%2C%22fromPage%22%3A%22search%22%7D&pdp_npi=6%40dis%21PLN%2114.19%2114.19%21%21%2127.10%2127.10%21%402103890117670371904623939e7a09%2112000029826005658%21sea%21PL%21911166357%21X%211%210%21n_tag%3A-29919%3Bd%3Ae76cfd63%3Bm03_new_user%3A-29895&curPageLogUid=7VGqfUTJj1SP&utparam-url=scene%3Asearch%7Cquery_from%3A%7Cx_object_id%3A1005004611084838%7C_p_origin_prod%3A&search_p4p_id=202512291139502324835655535800004893540_1&gatewayAdapt=glo2usa4itemAdapt

Those shunts are for 75mV. Some of the INA chips, like INA219 and INA228, can handle higher shunt voltages, up to 320mV for INA219, and 160mV (fixed) for INA228. But that would still work fine, would just be a resolution-related issue.

allows you to select a current in the range [1-1022 A], but there's still no option to change the shunt,

Well, I can limit that max. value to, say, 30A, I just added the max current setting as it is required for the new library I'm using.

These currents don't bother me at all, so they can stay as they are.

I've changed the resolution for the Shunt setting, and added more options for high-current shunts, to better match those to the Max. current setting.
@Gonzol999 Here's a Custom Energy build for ESP8266 for testing:
ESP_Easy_mega_20251230_energy_ESP8266_4M1M.zip

I don't have a shunt at home because I don't measure such high currents. I downloaded your binary; in my opinion, it offers much more options. I'll get myself a shunt, let's say the smallest one, and run some tests. Thanks again.

#2622
in this thread there is a link from which I downloaded the binary

This is an old link from November 18, 2021. Your request for the source code is also in this thread.

I have used the Zanduino INA library for adding support for the extra INAxxx models, though I haven't compared notes with the wollewald (INA226 explicit) library, as it is quite different.

What did you use for Averaging samples setting? As leaving that at 1 might turn out to be rather unstable. Also the Conversion rate settings may benefit the stability when allowing some more time for the conversion.

Averaging samples: I tested probably all of them from this list, the closest current readings gave a value of 16. Conversion rate Current: I also tested all values ​​from the selection list, here the closest current consumption readings give a value of 1. Despite all this, the current measurement is unstable and significantly different from the actual one.

Where do you have the shunt? At the GND level or at the + side?
What voltage do you use?
Do you live in a 60Hz net frequency area or 50 Hz?
How long are the wires between the INA226 and the shunt?

In the datasheet on page 14, there is some suggestion of filtering.

I'm discussing the code with Ton (via Signal) right now and we already found a few things that can be improved in the code.
So I guess Ton is already either writing this down for tomorrow or busy hacking the code :)

Also what current are you trying to measure?
Is it somewhat in the middle of the range of the shunt?
Or are you using a 30A shunt and try to measure 10 mA? (or some extreme like that)

I noticed a few places in the code of the library where quite a bit of resolution is lost due to careless calculations or completely illogical stripping of bits.

I've connected the shunt according to the attached diagram. The wires from the shunt to the INA are a few cm long (less than 10 cm). The voltage I'm trying to measure is 28 V, and these are external batteries connected to the UPS. The current from the mains should be 0 A under normal operation, but it can exceed 20 A under load. I live in Poland on a 240V 50 Hz grid.

The measurement results are very unstable, but I can probably check them with a filtering system at night. I'm just wondering why the binary I mentioned yesterday is practically OK.

I can't reach the home-garden.org site from my location (time-out), not sure if it still is available, or blocked for some reason, so there is no source-code available for comparison.
As TD-er said, there is room for improvement, so I'm working on that.

Ok. I'll check with the filtering system. Another question: Has anyone else tested the INA226 with your input?

I tested with the on-board shunt and a quite low current. Haven't payed much attention to stable output, other than it stayed constant, as was to be expected, and changed when I changed the 'load'.

I'm personally not a fan of measuring current on the 'high side', but it should work as the voltage doesn't exceed the max. input of the INA226.
As a simple form of filtering, you could try to twist the wires from the shunt to the INA226 chip.
A UPS may add some magnetic interference to the signal and with twisted wires you can prevent that.

There are lots of reasons why the other binary file yielded more stable results.
For example Ton's code does not (yet) wait for a read cycle to be finished. Just assumes it is.
Also the load from the UPS on the batteries can be fluctuating a lot within 20 msec (1 cycle of 50 Hz), meaning the sensor should perform a number of measurements over a multiple of 10 msec (or 20) or maybe even a continuous reading.
Not sure what is possible here as I've not read the entire datasheet.
I know there are several 'integration time' settings and I've also seen some averaging parameters.
Maybe it best to configure the sensor to take some 1 msec readings and then average over 500 or 1000 samples. This would then result in more 'stable' readings, but on the other hand it will also result in some delay as every filtering introduces a delay in the response to changes.
Also it may require some tweaking as the shunt and voltage are read sequentially by the same ADC. So longer integration times can result in completely useless power calculations if the current fluctates a lot during a 50Hz cycle.

Apart from this, there are still some parts of the code that can be optimized as quite a lot of resolution can be lost how it is done right now.

Hello friends, you can add "ESP_Easy_mega_20251228_energy_ESP32_4M316k"RTC DS3231 and TFT LCD _P095_ILI9341 to the firmware, or tell me where to download the plugin with support for INA3231, INA226, etc., to try to build the firmware yourself.

We have documentation on how to set up a local development environment here. It is mostly describing how to develop a new plugin or feature, but also briefly explains how to build a Custom ESPEasy, containing exactly the plugins and features you want to use.

A much simpler solution, btw, is to get an ESP32 board with 8MB or 16MB of flash (ESP32 Classic, ESP32-S3, ESP32-C3 or ESP32-C6), and install one of the MAX builds that includes (nearly) all features and plugins.

Hi, thanks for the link. And where can I download the max firmware? I didn't come across any, or I was looking in the wrong place.

"tonhuisman" thank you for guiding me in the right direction, found the MAX firmware on your MAX forum, soldered the flash drive on my ESP32 Wroom to a 16M flash drive, filled in the firmware and everything worked.

found the MAX firmware on your MAX forum

Not sure what you're talking about here, but official Release builds are available from our Github Releases page (for flashing via a local tool) or from the WebFlasher at https://TD-er.nl/ESPEasy,
and the current development branch (mega) is irregularly made available at https://TD-er.nl/ESPEasy/latest

@Gonzol999 Here's a fresh build for you to test, it has the calculation improvement, mentioned above, and also checks if a measurement result is available before retrieving it, for improved stability of results.
ESP_Easy_mega_20260125_energy_ESP8266_4M1M.zip

NB: This build is based on the 20260108 release, without the hotfix that was released today, as it's a test build. It will be updated to the mega development branch later.

The current readings are stable but unrealistic. I'm testing a current of about 3 A, and the ESP with the current load shows 2732.02 A.
What is the purpose of the Max. Current: checkbox if there's a shunt resistor:?

Hmm sounds like a mixup of mA and uA somewhere. (or mV vs uV)

Have you tested this yourself, or has anyone else done it? Maybe the problem is how I do it.

The current readings are stable but unrealistic. I'm testing a current of about 3 A, and the ESP with the current load shows 2732.02 A.

It's not obvious from either the configuration or the documentation, but this plugin shows the Current values in mA, as it always has. It seems that the value is in the expected range. You can use the Formula field to convert to A, if desired.

What is the purpose of the Max. Current: checkbox if there's a shunt resistor:?

The actual current to measure doesn't have to match the capacity of the shunt, then only a part of the 75mV output is being used.
The Max. expected current setting (as documented but not yet published) is used to set the resolution as optimal as possible. If high currents are expected, then the range is larger, so resolution is lowered, but also reducing precision.

Thanks for the replies.

If the plugin is supposed to return measurement results in mA, then it's probably OK. Yesterday, I solved the problem with the formula, dividing the measured value by 1000. You've clarified my doubts about the measurement range selection field. I'll continue testing your results with other settings.

Do you have other chips which are also supported by this plugin?
If so, I would greatly appreciate it if you could also try those on the same setup, just to make sure switching chip-models is also working properly and there isn't something else which is not intuitive.

Ton did move quite a lot of code around, so it is possible something got overlooked.

I already have an INA228 at home, but I'm still waiting for the ESP32 from AliExpress. Testing would need to be done on the ESP32. For testing, I need to build a receiver with a more stable current source, preferably a resistor, because as you mentioned earlier, a UPS isn't the best receiver for such tests. But I can still test.

Hello everyone.

I started testing the INA228 plug-in today, still with a low voltage of around 14V and a very low current of around 0.2A. The voltage measurements are OK, but the current is significantly off. The value measured by the plug-in fluctuates between 1.86 and 5.37mA. If, as Ton wrote earlier, the plug-in returns a value in mA, this result is outrageous. The board has a standard shunt resistor of 0.002Ω, and I have the Max. Current set to the lowest range, which is 1A. I noticed another problem: in the Tools/Interfaces tab, there's an I2C Scan tool. The Supported Devices field should indicate which module was found on the bus, but it's blank. The same is true for the INA226, so it's probably the plug-in's fault. One more question: INA228 modules have GPIO alerts. Do you plan to support this feature in the plug-in?

but the current is significantly off.

Hm, that's somewhat unexpected. I recently (today) received an INA228. I'll hook that up and see what results I can achieve.

... I2C Scan tool. The Supported Devices field should indicate which module was found on the bus, but it's blank. The same is true for the INA226, so it's probably the plug-in's fault.

Depending on the build, many known device names are included. For ESP8266 builds these names are not included for space reasons.

One more question: INA228 modules have GPIO alerts. Do you plan to support this feature in the plug-in?

That's currently not planned.

ale prąd jest znacznie odchylony.

Hm, to trochę nieoczekiwane. Niedawno (dzisiaj) dostałem INA228. Podłączę go i zobaczę, jakie efekty uda mi się osiągnąć.

With our voltages, the discrepancies and instability in the reading are similar. It's possible that my INA228 board is of poor quality. How are your tests?

... Narzędzie skanujące I2C. Pole „Obsługiwane urządzenia” powinno wskazywać, który moduł został znaleziony na magistrali, ale jest puste. To samo dotyczy INA226, więc prawdopodobnie wina leży po stronie wtyczki.

W zależności od wersji, uwzględniono wiele znanych nazw urządzeń. W przypadku wersji ESP8266 nazwy te nie są uwzględniane ze względu na brak miejsca.

This is not a problem, the found module address is returned and if someone connects the module to the I2C bus, they probably know what they are connecting

Jeszcze jedno pytanie: moduły INA228 mają alerty GPIO. Czy planujecie obsługę tej funkcji we wtyczce?

Na razie nie ma takich planów.

this is also not a problem, similar functionality can be achieved using rules and e.g. the ESP GPIO port